This file contains information that was not available when the Aldus FreeHand 3.1 documentation was printed. Sections 1 through 3 apply to both versions 3.1 and 3.11. Sections 4 through 8 are new for Aldus FreeHand 3.11.
1. Installation information
2. Corrections to the “Guide to Installation, System 7.0 Compatibility, and Feature Updates”
3. Additional information about System 7.0
4. PICT previews of EPS files
5. Aldus Fetch support
6. Network copy protection
7. TruMatch colour library support
8. Binary TIFF printing
The installation program also installs two additional ReadMe files:
• The “Aldus FreeHand 3.1 PPD ReadMe” file, which lists the PPD files included with Aldus FreeHand 3.1 and the printers they drive. This file also includes a brief explanation of the new PDX Editor.
• The “Aldus FreeHand 3.0 ReadMe” file, which includes corrections to the version 3.0 documentation set.
Please read these files before you begin working with Aldus FreeHand 3.1 for Apple Macintosh computers. We also recommend that you print copies of these files to keep with your documentation.
-------------------------------------------
1. INSTALLING ALDUS FREEHAND 3.1
-------------------------------------------
• All current versions of Aldus FreeHand, Persuasion, PageMaker, and PrePrint use the Aldus Installer/Utility to install program files. To avoid any problems, only use the Aldus Installer/Utility provided with Aldus FreeHand 3.1.
• If you’re running under System 7.0, and you’ve created an alias for the Aldus folder, remove the alias before installing Aldus FreeHand 3.1. Otherwise, the installer may not install the Aldus FreeHand files correctly.
• If you want to keep Aldus FreeHand 3.0 on your hard drive when you install Aldus FreeHand 3.1, move the FreeHand filters file from the Aldus folder in your System folder into the folder with Aldus FreeHand 3.0 before you install the new version. When you install Aldus FreeHand 3.1, a new FreeHand filters file is installed in the folder. Each filters file works best with the version with which it is provided. (Note for users of EPS Exchange by Altsys Corporation: EPS Exchange is compatible with versions 3.0 and 3.1, of Aldus FreeHand, so you can leave this file in the Aldus folder.)
• Aldus FreeHand 3.1 and 3.11 use the same filters file, so you don’t need to move the file from the Aldus folder when you install version 3.11.
• During installation, information is added to the “FreeHand filters” file that could activate virus-detecting software resident on your hard disk. To avoid errors during installation, we strongly recommend that you disable or remove any virus-detecting software before installing Aldus FreeHand 3.1, and then reactivate or replace such software after the installation.
• The Aldus Installer/Utility installs program files in specific locations, such as the Aldus folder in the System folder. We recommend that you accept the default folder structure. Do not move key program files around unless you understand how Aldus FreeHand works with these files. (Aldus FreeHand looks for program files, such as the Aldus FreeHand Defaults file, in certain locations.)
• Because Aldus FreeHand shares a common Installer/Utility with other Aldus programs, some items listed on the “Diagnostics” pop-up menu do not pertain to Aldus FreeHand. One item, for example, contains the phrase “Search for printer files and Aldus Prep,” but Aldus FreeHand does not actually use Aldus Prep. If you accidentally search for printer files and Aldus Prep during installation, press Command + period (.) to stop the search.
• If you’ve modified your Aldus FreeHand APD files and want to use them with Aldus FreeHand 3.1, move the APD files into the PPDs folder (located in the Aldus folder in your System folder). However, we strongly suggest that you modify the corresponding PPD files as soon as possible, and then discard the APD files. PPD files contain optimized screen angles and rulings that substantially reduce moiré patterns in colour output. PPD and PDX files also allow you to calibrate imagesetter output.
• The number of PPD and PDX files present in your PPDs folder affects the time it takes for the “Print options” dialog box to appear when you click the “Change…” button in the printing dialog box. To reduce the time required for this dialog box to appear, install only the PPD and PDX files you need, or remove unneeded PPD and PDX files.
• To install individual PPD and PDX files after you’ve installed Aldus FreeHand, first install the Aldus Installer/Utility on your hard drive. Then, locate the PPD or PDX file on the installation disk set that you want to install, and double-click that file to launch the installer. The installer prompts you to save the file to a designated location. We recommend saving it in the PPDs folder in the Aldus folder in your System folder.
“Aldus hotlinks,” page 23: The second bullet following Step 3 is incorrect. If you save a publishing file with a new name, both the original file and the new file are linked to the edition file. The edition file is updated with changes from the most recently saved publishing file. To break or control the link between one of these files and the edition file, you must either move one of the publishing files or open one of the publishing files, choose “Publisher options…” from the “Edition” submenu on the Edit menu, and click “Manual.” When “Manual” is selected, changes are only sent to the edition file if you choose to send them.
Note: Having more than one publishing file for an edition file is not recommended. If you must save a publishing file with a new name, first choose “Save” from the File menu to save the original publishing file. Then, choose “Save as…” from the File menu. If you don’t save the files in this order, you may run into problems with how the edition files link to them.
“CMYK TIFF Support,” page 60: The correct name for the DCS file format is Desktop Colour Separations.
• Aldus FreeHand 3.1 is fully compatible with the new Macintosh 68040-based computers, which include the Quadra 700 and Quadra 900 series.
• Only the Macintosh IIsi, IIci, and IIfx and the new 68040-based computers currently use 32-bit addressing. To set the 32-bit addressing option, choose “Control panels” from the Apple menu, double-click the “Memory” icon, and click “32-bit addressing” to turn the feature on or off. Some third-party products (INITs) are available to make other Macintosh computers compatible with 32-bit addressing. Talk to your computer dealer (or call Apple Computer) for more information about these products.
***System 7.0 section***
• Apple recommends a standard keyboard shortcut for launching a publishing application and opening the publishing file (publisher) for a subscriber. The recommended shortcut—pressing the Option key and double-clicking the subscriber—opens the various “Element info” dialog boxes in Aldus FreeHand, so we were not able to implement this keyboard shortcut.
• To edit the publishing file for a subscriber in Aldus FreeHand, select the subscriber and choose “Edit original” from the “Editions” submenu on the Edit menu, or select the subscriber, choose “Subscriber options…” from the Edit menu, and click “Launch Publisher.” Other Aldus applications, such as Aldus PageMaker 4.2, use Apple’s recommended keyboard shortcut.
• If you subscribe to an Adobe PhotoShop PICT edition file from Aldus FreeHand, you may not be able to update a subscribing file with changes saved to that edition file. If this problem occurs, Aldus FreeHand displays the following message when you open the subscribing file: “Could not complete your request because there is not enough memory.” You should then delete the subscriber, and subscribe again to the updated PhotoShop PICT edition file.
• If you subscribe to an edition file, delete that edition file, and then create another edition file with the same name and location, the subscriber will automatically link to the new edition file. You can use this technique to replace a subscriber automatically. Otherwise, you should avoid giving an edition file the same name and location as a deleted edition file.
• If you publish or subscribe to an edition file and then move the publishing or subscribing file to a computer with System 6.X, a message appears when you open the file alerting you that you cannot make changes to an edition file or update subscribing files with changes from an edition file. Once you move the file back to a computer with System 7.0 and relink with the edition file, you can update the edition and subscribing files with any changes. (Aldus FreeHand prompts you to find the edition file again when you open the publishing or subscribing file under System 7.0.)
• Aldus FreeHand 3.1 and Aldus PageMaker 4.2 use hotlinks to dynamically link an Aldus FreeHand EPS file (placed in either Aldus FreeHand or PageMaker) and the file from which you exported it. The command that activates the hotlink, “Edit original,” performs similarly in Aldus FreeHand and PageMaker when you’re editing placed Aldus FreeHand EPS files. However, there are also some significant differences in how the “Edit original” command works, where it’s located on the Edit menu, what keyboard shortcut activates it, and so on. Be sure to read the Aldus FreeHand 3.1 and PageMaker 4.2 documentation for a complete explanation of how the command works in each program.
• You can use hotlinks to open the original illustration for an exported Aldus FreeHand EPS file, but not to open the original illustration for an exported Aldus FreeHand PICT or PICT2 file.
• Balloon Help may cause redraw problems for the online help system. If you have Balloon Help turned on, and you open Aldus FreeHand online help, be careful not to move your pointer tool outside the Help window. If you do and a balloon opens, it temporarily erases any text that appears beneath it. If you move the pointer tool over the toolbox, the text from the online Help system may appear in the toolbox. To restore the screen, close the online Help system and the toolbox, and then open each of them again. To avoid these screen redraw problems, do not run Balloon Help and online Help at the same time.
***New Features in Aldus FreeHand 3.1***
File compatibility with Aldus FreeHand 3.0 for Windows, pgs 32-34:
• If you save a file as a template in Aldus FreeHand version 3.0 for Windows, and then open it in Aldus FreeHand 3.1 for the Macintosh, the file opens as a regular illustration file. You can then save it again in template format. If you’ve installed System 7.0, you can also convert the illustration file to a stationery pad, and open multiple copies of it.
• If you create an illustration containing EPS, PICT, or TIFF subscribers in Aldus FreeHand 3.1 for the Macintosh, and then open that file in Aldus FreeHand for Windows, those elements are treated as PICT, TIFF, or EPS elements. You can ungroup and edit a PICT subscriber, for example, and you can choose “Element info…” from the Element menu to modify a TIFF or EPS subscriber. If you open the file on the Macintosh again, however, the subscribers are no longer linked to the edition files.
Enhanced features for creating your illustrations, pgs. 34-47
• If you’re using a WACOM digitizer with the new pressure-sensitive freehand tool, turn the tablet on before you launch Aldus FreeHand. Turning the digitizer on after launching the program may cause the “Colours,” “Layers,” and “Styles” palettes to expand to fill the illustration window.
• Aldus FreeHand uses Adobe Type Manager (ATM) 2.X to convert text to paths, so that the text converts faster. If you don’t have ATM 2.X, then Aldus FreeHand uses the PostScript font file to convert text to paths.
• In Aldus FreeHand 3.0, you can distort a grouped element as you transform it by selecting the grouped element, choosing “Element info…” from the Element menu, and checking “Group transforms as a unit.” Aldus FreeHand 3.1 lets you check “Group transforms as a unit” as you group the elements, saving you the extra step of opening an “Element info” dialog box. To do this, select the elements that you want to group, and then hold down Shift as you choose “Group” from the Element menu (or press Shift + Command + G).
• When you place an Aldus FreeHand 3.0 EPS file that contains text into an Aldus FreeHand illustration, the screen image may not match the printed version if you’re running under System 6.0 and you magnify your view of the EPS file greater than 100 percent. (You may also experience slower redraw when you magnify your view of the EPS file.) The EPS file will print correctly, however. Aldus FreeHand 3.1 EPS files display correctly at any view under System 6.0.
• Applying a style from the “Style” submenu on the Type menu (such as “Bold” or “Italic”) to a plain text block may cause any stylized fonts (such as B Helvetica Bold) that you subsequently apply to that text to print incorrectly. Instead of printing the stylized font, Aldus FreeHand may print a plain version of the font. Once the problem occurs (you print a file and the text prints without the correct stylized font), it will reoccur in every illustration file you open until you quit Aldus FreeHand and start the program again. When you restart Aldus FreeHand, you can then open the file in which the problem occurred and apply the stylized font to the text again, and it will print properly.
To prevent this problem, either avoid using stylized font families (use merged fonts instead), or avoid applying styles from the “Style” submenu on the Type menu (or the “Style” pop-up menu in the “Type specifications” dialog box) when you use stylized font families. If you apply a stylized font first, the problem does not occur.
More control and speed in printing, pages 52-58
• If you have trouble printing an Aldus FreeHand file, see if you have the DeskPict INIT installed on your hard drive. We have noted occasional printing problems when this INIT is present. In general, if you have printing problems, you should check for conflicts by removing each Cdev, INIT, or Extension file one at a time, and then try to print again.
• The System 7.0 printer driver lets you print an Aldus FreeHand illustration as a PostScript file by simply clicking “PostScript® File” for “Destination.” (You click “Printer” to print the illustration on a printer.) To open the printing dialog box, choose “Print…” from the File menu. If you are running under System 7.0, you can use this technique instead of the one described on pages 291-292 of the “Aldus FreeHand 3.0 User Manual.”
• The L300*.PDX files included with Aldus FreeHand 3.1 contain two additional paper sizes: “Letter.extra.transverse – C & D” and “Tabloid.extra - C & D.” Choose these paper sizes if you plan to print to Linotronic Cora or Densy model imagesetters. The Linotronic Cora and Densy imagesetters have a smaller maximum image area (approximately 11.7") than more recent imagesetters (approximately 12"). If you try to print on a Linotronic Cora or Densy imagesetter with the standard “Letter.extra.transverse” and “Tabloid.extra paper” sizes, you’ll get a PostScript error when you print.
Expanded import and export capabilities, pages 59-64
• Aldus FreeHand 3.1 allows you to export illustration files in PICT and PICT2 formats for use in other programs. These formats have limitations, however, so we strongly recommend that you export your illustrations in EPS format unless you need to import it into a program that doesn’t support EPS, or you need to edit the graphic in another program. When you export an illustration in PICT or PICT2 formats, the file may lose the following information when you import it back into Aldus FreeHand or into another program:
- Graduated and radial fills
- Elements that are pasted inside other elements
- Tiled fills
- Custom and PostScript line and fill effects, which convert to solid black
- Composite paths
- Dashed strokes on paths
- Fractional point sizes applied to text
- Kerning pairs in text and manual kerning information
- Detail in curved paths that are small and complex, such as text converted to paths
Some programs are better than others at importing information in PICT format. Aldus FreeHand, for example, does not maintain path clipping information when you import PICT files, so graduated and radial fills and elements pasted inside other elements, which are stored in the PICT file, do not appear in the imported graphic.
• When you export files in PICT format that contain any of Aldus FreeHand’s 65 patterned fills and lines, Aldus FreeHand substitutes one of the nine patterned fills or lines that the LaserWriter recognizes and correlates them to shades of grey. This ensures the best printed results possible. This limitation only affects illustrations exported in PICT (not PICT2) format.
• If you export an Aldus FreeHand illustration in PICT or PICT2 format and then import it into Aldus Persuasion, you may get unexpected results. In Persuasion, the bounding box for the imported PICT or PICT2 graphic will be larger than the actual graphic. You must ungroup the Aldus FreeHand 3.1 PICT file to print it from the Persuasion file. If you ungroup the PICT or PICT2 graphic to edit it, however, the graphic elements will expand to fill the enlarged bounding box.
• If you’re using a monochrome monitor when you export an Aldus FreeHand EPS file that contains colours, the EPS file appears in black-and-white on your screen when you import it into another file—even if you’ve switched to a colour monitor. The EPS file will print the colours correctly, however. (If you’re using a colour monitor when you export the file, then the colour information will display on the screen when you place the EPS file.)
• If you export an Aldus FreeHand file in MS-DOS EPS format, Aldus FreeHand automatically unchecks the “Binary TIFF” option because MS-DOS applications cannot print binary TIFF images. You can check this option, if you want, before you export the MS-DOS EPS file.
Aldus FreeHand 3.11 allows you to attach either of two types of PICT previews to EPS files: object-oriented (as in version 3.1) or bitmapped (as in version 3.0 or earlier). There are advantages and disadvantages to both, although we recommend using object-oriented PICTs.
• Object-oriented PICTs have several advantages: They are generally smaller, unless your illustration contains complex fills, such as custom, PostScript, tiled or patterned; they scale more accurately; they render at the resolution of the output device; the quality is better if you use FreeHand EPS files in Persuasion and output to a QuickDraw slide recorder; and the screen image (colour or black and white) depends on the monitor settings. For example, if your computer has colour ROMs and you set your monitor to black and white, the screen image will be black and white, even though the file is saved with colour.
• Bitmapped PICTs are generally larger, although their file size doesn’t vary with the complexity of the illustration; they scale poorly; and if your computer has colour ROMs, the screen image will be colour, regardless of the monitor settings.
To control the type of PICT preview you create:
1. Choose “Preferences…” from the File menu.
2. Click the “More…” button to display the “More preferences” dialog box.
3. Click to check or uncheck the “Generate EPS previews as bitmaps” option. The default setting is checked, which means previews are created as bitmaps. Once the option is checked (or unchecked), it remains that way for all illustrations until you change it.
The type of PICT preview you create determines the type of Fetch preview you create. It also affects items published (via Publish & Subscribe), and items copied to the Clipboard; it does not affect exported PICT or PICT2 files.
Aldus FreeHand 3.11 includes support for Aldus Fetch, a program that can catalog thousands of graphic items in a single database and provide instant visual access to the cataloged items. Aldus FreeHand supports Fetch in two ways: you can include a Fetch preview with your illustration, which you can view as either a thumbnail or full-screen image, and you can annotate the Fetch preview with keywords and descriptive text to help search for and retrieve it within the Fetch catalog. Once you find the image, you can use the preview in another application, or launch any application that can edit the file.
A Fetch preview can be attached to any file format saved or exported from Aldus FreeHand, including EPS Exchange formats. The Fetch preview can be either an object-oriented or a bitmapped PICT, depending on how your preferences are set.
An Aldus FreeHand native file can be saved with a Fetch preview. (A native file is the actual Aldus FreeHand file that you save, as opposed to an Aldus FreeHand graphic, which you export in either EPS or PICT file format.) A native file does not contain EPS information and cannot be used for high-quality printing, except when printing from FreeHand. However, a Fetch preview created from an Aldus FreeHand native file can be used as a graphic in applications not requiring EPS graphics.
Before you create a Fetch preview, consider how you will use it within the Fetch catalog. Some scenarios follow:
• If you need to edit an Aldus FreeHand illustration before using it in another application (for example, in a PageMaker publication), and you want to use Aldus FreeHand to edit it, you can create a PICT preview when you save the original Aldus FreeHand illustration. Then you can catalog the PICT preview in the Fetch database. The PICT preview does not contain EPS information and cannot be used for high-quality printing without opening the native file in Aldus FreeHand and exporting it as an EPS file. However, because the preview is attached to a native FreeHand file, there is a direct link between the Fetch preview and the original file, so you can open the illustration directly from the Fetch catalog.
• If you need a graphic that will offer high-quality printing, you can export the illustration as an EPS file. However, you cannot directly open the EPS file from the Fetch catalog. Instead, you must launch Aldus FreeHand, open the native file that corresponds to the EPS file in Fetch, edit it, and then export a new EPS file. We recommend that you annotate your Fetch preview with the filename and location of the Aldus FreeHand native file before exporting it. (See the annotation steps below.)
• If you need to edit an Aldus FreeHand illustration in an application that can edit colour bitmaps or PICT images, you can use a Fetch preview.
To create a Fetch preview of your illustration:
1. Choose “Preferences…” from the File menu.
2. Click “More…” to display the “More preferences” dialog box.
3. Decide which type of Fetch preview you want (object or bitmap), and click to check or uncheck “Generate EPS previews as bitmaps.” Once the option is checked (or unchecked), it remains that way for all illustrations until you change it.
(Note: If you need more information on the advantages and disadvantages of object and bitmap PICTs, see section 5 of this ReadMe file.)
4. Click “Include Fetch preview” to attach a Fetch preview of your illustration to the EPS file. Once the option is checked (or unchecked), it remains that way for all illustrations until you change it.
(Note: If you don’t use Fetch, make sure the “Include Fetch preview” option is unchecked to minimize file size.)
5. Click “OK” to close the dialog box.
To annotate the Fetch preview:
1. Choose “Annotate Fetch Preview…” from the File menu.
2. In the “Annotate preview” dialog box, type keywords, separated by commas, and descriptive text as desired. For example, if you plan to edit the graphic in another application, we recommend that you annotate the Fetch preview with the filename and location so you can find it.
3. Click “OK” to close the dialog box.
To create Fetch previews of your existing Aldus FreeHand illustrations, open an existing illustration in version 3.11, and follow the steps above to create a Fetch preview and then annotate it.
If you do not want to annotate the preview when you create it, you will need to manipulate the illustration in some way to enable the “Save” option on the File menu. For example, you could add and then delete an element, or delete an existing element, then undo the deletion. You must save the illustration in order to create a Fetch preview. If you close the illustration without saving, the Fetch preview is not created.
For more information on how to use Aldus Fetch, see the “Aldus Fetch User Guide.”
Your Aldus FreeHand license agreement authorizes you to use only one copy of Aldus FreeHand for each set of installation disks you purchase.
If you run Aldus FreeHand 3.11 while connected to a network, the program checks the network to see if a copy of the program using the same serial number is already running. If it finds that the same serial number is in use, an alert box appears.
Click “OK” to close the alert box. Whoever is using a copy of Aldus FreeHand with the same serial number must then quit before you can launch the copy that you want to use.
Aldus FreeHand also queries the network when you print a publication. If it finds a copy of the program with an identical serial number, the program stops printing and quits. You’ll be able to save your publication before the program quits.
If the network fails while Aldus FreeHand is checking for duplicate serial numbers, a significant amount of time may pass before the alert box appears. Normally, this alert box appears quickly if a duplicate is found.
Aldus FreeHand 3.11 now supports the TruMatch digital colour-matching system with five TruMatch colour libraries. TruMatch colour libraries contain only process colours. If you want to convert any of these colours to spot colours, you must first import them as process colours, and then edit them in the “Colours” dialog box.
Note: Be sure to consider your printing needs when choosing the colour method for your job. The TruMatch system is optimized for process colour printing. If you want spot colours, we recommend that you use a colour library that contains spot colours, such as PANTONE, rather than converting process colours to spot. In addition, if you convert a process colour to spot and then back to process, the specifications may not match the original. You will need to import the colour again.
To select a colour from a TruMatch library:
1. Choose “Import…” from the “Colours” palette submenu.
2. Select a library from the list, and click the “Open” button.
3. Select the colours you want to include in your illustration, and then click “OK.” The colours are added to the “Colours” palette, the “Colours” dialog box, and all the Colour pop-up menus.
To convert a process colour to spot:
1. Select the colour in the “Colours” palette.
2. Choose “Edit…” from the “Colours” palette submenu.
3. On the “Colours” dialog box, select “Spot,” and change the colour model if needed.
4. Change the colour values if needed, and then click “OK.”
If you experience network connection problems when printing TIFF images from Aldus FreeHand, you can output the TIFF as ASCII data instead of binary. Note that binary TIFF output is faster than ASCII.
To disable binary TIFF output, uncheck the “Binary TIFF” option in the “Print…” dialog box.
